I find it rediculous that such a problem could go unnoticed and unfixed by Microsoft for so long, and that it took a Microsoft participant on a programmer's blog reading about it to track down and correct the issue.
U:\>w32tm /monitor /computers:time.windows.com,us.pool.ntp.org
NTP: +0.0541156s offset from local clock
RefID: time-nw.nist.gov [184.108.40.206]
NTP: +0.0293621s offset from local clock
RefID: bigben.ucsd.edu [220.127.116.11]