I seem to recall someone else testing it and saying it was there. I see no reason for MS to suddenly fix this bug as I doubt they would consider it an important one. Even if it is fixed you should still code to avoid it for all the users of older versions.
I was just curious to see if MS had actually updated much, they are pretty useless in my opinion, but thats besides the point. Thanks for the fix by the way, it came in useful for me