A bad fix for the consistent trace problem

A trace should always include data generated in the relevant interleaving. If a
trace includes 'dynamically generated' data (e.g. PIDs, references, etc.) these
should all be updated if a new interleaving is started.

However, simply 'patching' the 'short log' of actions (lid_trace) is not enough,
as there might also be dependencies that need the most recent data. The attached
regress testcase exposes such a bug which must be fixed.