Setting Break Points in Loops.

Last time I used Construct 2, I had a problem with loops being completely opaque to the debugger. I couldn't figure out how to test for program state while in a loop which makes certain types of games like grid based games difficult to build. Is this limitation still the same in Construct 2? Are there any alternative methods that can be used that are interactive and don't require logging?

Thanks!

Maybe I'm thinking about it wrong? Maybe I need to approach a grid based game by replacing complex looping logic with set based logic? Would that work? Would the same information be visible that I would typically find while watching program state in a loop?