In today's edition of "Is this any better now that it isn't crashing?", I'd like to show you a very interesting test case with loop widening.
Looking at the included test case, it's immediately obvious that this is not only a false positive, but also a very bad bug report in general. We can see how the analyzer mistakenly invalidated b, instead of its pointee, resulting in it reporting a null pointer dereference error. Not only that, the point at which this change of value is noted at is at the loop, rather then at the method call.
It turns out that FindLastStoreVisitor works correctly, rather the supplied explodedgraph is faulty, because BlockEdge really is the ProgramPoint where this happens.
So it's fair to say that this needs improving on multiple fronts. In any case, at least the crash is gone.