ElapsedTimeStrategy::hasElapsed is confusing for variety of reasons:

• creating ElapsedTimeStrategy is incomplete if it's not followed by calling hasElapsed
• it doesn't do any wait, while one may can expect it does
• the main task is actually it's side effect to set new upper time limit for the strategy

Refactor it to avoid side affects.