Only look for values allocated in the entry block.
For now, just ignore fragile test's failure.

The test fails even when there's nothing wrong but the .dot file happens to get transitions generated in a different order than expected. Until we fix this by using a more stable output representation to check against, just ignore the test result.
Drop unused function.
Use BaseName(Argument&) rather than Arg.name().

Some Arguments, like indirect args or structure field, don't have a name() set.
Update operator==(Argument&,Argument&).

We updated the definition of Argument some time ago but did not update its operator== to recurse through the new members.

I really, *really* wish that protobufs just generated this code!
Record Arguments, not ValueDecl references.

The top-level list of arguments referenced by an assertion should be arguments (which may be indirect or fields), not just variables that have C ValueDecls.