Klever

Native Scheduler can decide to speculatively shrink memory limits for tasks that can result into they are solved twice when first attempts fail. Unfortunately, just resources spent on successful runs are reported while information on wall and CPU time spent for speculative failing tasks are not tracked.

Most likely, we need to introduce one more wall time measurement and one more CPU time measurement to track speculative wall and CPU time since otherwise we will influence speculative verification results.