Fix a receive had-after bug in the dependency relation

An identical message from another process could be erroneously identified
as the one that was received in a receive statement with an after clause.
This caused additional interleavings (to reorder the receive and send
statements) which were uninteresting, since the receive statement would
receive another message anyway.