if I hover over the second i and the execution is in the seoond loop, it does not display i correctly.
It shows the value of i of the first loop.
Well, I know about this for quite some time, but I am not sure I can fix that. To understand the issue, our ability is limited by what the debugging API gives us. I believe in this case, windows debugging api simply ignores second 'i'.
But I might be wrong. Will add to RM and try to investigate.