I spoke too soon about the cause.  This does occur in the command line version
also, but can be avoided by deleting the Cookies.txt file or turning off
Cookies and the Cache.  This does NOT seem to work in WinHTTrack.

So the following command-line works with HTTrack:
httrack.exe <http://www.ilounge.com/index.php/news/P0/index.html> -v -b0 -C0
-O iLounge

The following fails (on secondary and subsequent runs):
>httrack.exe <http://www.ilounge.com/index.php/news/P0/index.html> -v -O
iLounge

Interesting, huh?  I'm not sure if more changes will show up, but this seems
consistent so far.