I know what it means now, but...

The more I work with computers (and I've been working with them for 32 years), the more I'm amazed at how intricate and complicated the simplest problems can become.  I was baffled why other clients (litecoin, feathercoin) didn't have the problem with the time. I was confused that my virtual machines didn't have an issue even when set to use the host date/time.  But, after studying the util.cpp till I knew what to look for (thanks for all the suggestions), I was completely blown away when this showed up in the debug.log


This was from a fresh debug.log and all the entries occurred within about 1 minutes of each other.  I've stripped out all the extraneous IP connection and addressing lines.  Note that as it connected to peers, the time difference was quite consistent (aprox. 28 days) until all of a sudden after 9 connections, the difference went to zero, all while consistently showing me the correct date/time on my desktop.  It is consistent that every time I start the bitcoin-qt, the time is off about that much, but whether or not the difference goes away is inconsistent.  

If it was the bios that had the wrong time, it would not straighten itself out randomly without a reboot, and certainly not mess itself up simply by closing the bitcoin client and re-opening it. I have completely uninstalled the client and deleted the %appdata%\bitcoin directory and started over new, yet am right back where I started with only the mystery and few answers.  Something happened or got written someplace around May 20 that the client keeps reading.  What it is, I have no clue.