The problem is that the value is either being stored by Windows (or possible returned by Win32::GetTickCount() I haven't been able to find the info on this yet) as an 32-bit value. This gives a maximimum milliseconds counts of
4294967295 which translates to 49 days 15 hours 37 minutes 33.354 seconds.
If I manage to locate the information as to whether this is an OS limitation or if its the module wrapper that is throwing information away, I'll update this post.
Update: I found an appropriate page on msdn
The elapsed time is stored as a DWORD value. Therefore, the time will wrap around to zero if the system is run continuously for 49.7 days.
Okay you lot, get your wings on the left, halos on the right. It's one size fits all, and "No!", you can't have a different color.
Pick up your cloud down the end and "Yes" if you get allocated a grey one they are a bit damp under foot, but someone has to get them.
Get used to the wings fast cos its an 8 hour day...unless the Govenor calls for a cyclone or hurricane, in which case 16 hour shifts are mandatory.
Just be grateful that you arrived just as the tornado season finished. Them buggers are real work.