I got this answer from the Sharpziplib forum
Hello
This seems to be a WinZip error. I have not noticed this before.
I did this test:
1) Use WinZip to add the file to zip. In WinZip, click Properties and Details. Browse through the parts list and find the file timestamp.
2) Use SharpZipLib to create a similar zip file with the same input file. Open the result in Winzip and look at Properties> Details for the timestamp of the file.
My input file has a Modified timestamp (file properties) 2010-12-14 15:51:28, and in my test SharpZipLib correctly saved it in zip, and WinZip saved it as 2010-12-14 15: 51:30
In other words, WinZip added 2 seconds when it put it in a zip code. After extraction (with WinZip or SharpZip), Modified is now 15:51:30 instead of the original 15:51:28.
Surprisingly, such an obvious error in WinZip can be unregistered and uncommitted for so long. If you have a paid version, you should definitely raise an error with them.
I just remembered the 2 second drill down at the old 8.3 timeframes.
Quick google found this ...
Quote: โThe original DOS file system had only 32 bytes to represent the file in the directory. A very limited file name 8.3 and a limited degree of detail (2 seconds) in the file date are fixed in Win32 (VFAT) file systems.โ from http://www.xxcopy.com/xxcopy15.htm
The Zip format allows only 2-second detail in a standard timestamp entry. Date and time are encoded in the standard MS-DOS format.
An optional NTFS additional data field (0x000a) may be included, which may include the last modification time, last access time, and creation time. WinZip does not seem to create it. SharpZip will use it if it is present, but as far as I can see, it is not created when using FastZip to create a zip. This can be a useful option to add to your code. You can create it manually if you use ZipFile.
Hope this helps, David