ODv3 Timeout reached even if the real timeout was not elapsed

Odv3 uses a rcX Timer (Autoreload) which is started and stopped at the begin and the end of every work process. If at start up, the application creates a lot of objects, the start- and stop-timer functions will be called for each object. That may cause, that the timer events are erroneous triggered and timeout is reached even if the timeout value was not really elapsed.