If we know that every path from an alloca leads to a store, we can optimize away poisoning its shadow (it'll be overwritten anyway).
I'm wondering if there's a better approach for finding all these def-uses. I investigated the DominatorTree, but I'm not sure how I would use that to check *all* the uses without blowing up the runtime for instrumenting an alloca to O(N^2) (N=# uses) or so.
TODO: get rid of Const in this function name