Nope.

The bug was documented here by Paul Randal and allegedly fixed in a patch for SQL Server 2008 R2.

I read that it still existed in SQL Server 2012 so spun up a patch-free bug-ridden RTM instance and tried out his sample code.

It worked fine.