Seems this only happens If you order the output of a radom set by a row of newid values being created during the same transaction to delete values from the set. I would call the script buggy and write it in a way it worked long before I engaged microsoft to resolve something that IMHO: is working as expected.

Unless I was trying to write a trick question that would get more than 90% wrong answers. Those seem to be real popular these days.