Same here on my Macbook Pro 17" Core 2 duo. I know something about UNIX, and I know what's happening here. Mac OS X is based on Darwin, which is based on BSD code. This foundation probably causes the issue -- UNIX tends to assume that your clock is in GMT (UTC), and sometime in the software config you tell the OS what you prefer your timezone to be. Windows, based on DOS, is under the impression that everyone's PC is set to local time in the BIOS setup routine. This difference in opinion is pretty stupid, but that's the problem. The RTC (real-time clock) will get set by Windows to one thing using NTP, and by UNIX or Darwin or OS X to something else. Surely this issue is relatively old for anyone who dual-boots Windows and some other OS. This has been the case for over 10 years, so someone has figured it out. Or just be sure and connect to your LAN domain or the Internet every time you boot. Makes for some awful log files, I would imagine. I keep an NTP time server on my network, plus any Windows domain controller will force authenticating clients to have the correct time. (which is whatever the DC's time happens to be, synchronized or not)
I think that most unixes allow you to force them to accept Window's opinion. I seriously doubt you can configure Windows to accept thw opinion of UNIX. A Darwin guy would know where to look.