As several people have pointed out, this "explanation" is bogus.

SQL Server is comparing these values as strings - this has nothing to do with datetime precision. Replace the '2011-07-31 00:00:00.000'...