Sometimes, we see a wrong argumentpath popping up, where it is not at all expected. It looks like reducing InvocationSequence's equality does the trick.

We'd guess, the problem is on looking up from LIMITED_VALUE_INVOCATIONS or PLACEHOLDER_BY_INVOCATION.

see attached patch, that works for us.

Please send a test case that fails with the current lambdaj source code, otherwise it will be impossible for me to validate this fix (or even understand what this is supposed to fix).