Replying to myself: The lock really seems to be the culprit. If the resource
is already locked then the stage doesn't need to wait and can continue with
the rest of the code. However Jenkins/the plugin/whoever still thinks that
this stage is waiting, therefore the wrong timing.
I replaced the lock with some other code and now the run times are
shown correctly.
bye Fabi