If we find a type that
- we think we can reason about statically
- does not have an __iter__ but can be iterated via __getitem__

we previously just bailed saying that we know it doesn't have an __iter__ method
(instead of calling getiterHelper like we should).  I think we've always had this,
we've just never run into it until testing the refcounting in llvm-only mode.