The only problem I've read about with respect to any timer problems in
.NET is a timer that has been configured to repeat, and which has been
left running for an extended period of time (I don't recall the
specifics, but "49 days" seems to pop into my head for some reason).

If your application is one that might be affected by this, my
understanding is that simply changing the timer usage so that you reset
the timer each time it is signaled, and start it again with a new
interval, it works fine.

If you expect there to be a problem, my suggestion is that you first
reproduce the problem in your own code.  Then you will have a better
idea of whether it's really a problem, and you will be able to ensure
that you have satisfactorily worked around the problem.

Pete

You should "code up" a timer.

http://groups.google.com/group/microsoft.public.dotnet.framework/browse_thread/t
hread/aa8a7a59b698f6b5/009395e3234a3dbc?lnk=st&q=sloan+%22Private+m_doTheWorkTim
er+As+Timer%22&rnum=3#009395e3234a3dbc

I think I have a link at the bottom of that post, which refs a MS KB article
about the "why".

or

http://groups.google.com/groups/search?q=sloan+%22Private+m_doTheWorkTimer+As+Ti
mer%22

or

http://msdn2.microsoft.com/en-us/library/system.threading.timercallback.aspx