This is another step in speeding up the testtool scripts.
In many cases where a sleep(...) is used it has shown that a WaitSlot(...) with
the same timeout settings is sufficient.

There were a couple of proposals on how to handle the transition.
1) Re-implement sleep(...) using WaitSlot() and force everyone to update the tests
2) Make the function interface compatible with unchanged behavior
3) Implement another function DynSleep(...) with a slightly modified interface.

1) Is bad and unrealistic because nobody is going to find the time to do it
2) + 3) Are equally suited/unsuited. 
Good: 
* No immediate action required by script owners
* Possibility to change all occurrences 

Bad:
* No immediate action required by script owners (is never going to completed)
* Each occurrence of a sleep() statement has to be evaluated