Fix some weirdness in PersistentInvocationLog's code structure
Fix some weirdness in PersistentInvocationLog's code structure

It's weird to create fingerprint entries and store paths in a vector
and then immediately after look them up in the hash table. More
stright forward to just store the fingerprint ids directly in the
vector.

per-gron/shuriken,per-gron/shuriken,per-gron/shuriken,per-gron/shuriken