Loop order on execution?

Dear Spotware,

When back testing Print statements I have in loops and indicators are grouped up as if they are run in parallel e.g.

Result Type C
Result Type C
Result Type C
Result Type B
Result Type B
Result Type B
Result Type A
Result Type A
Result Type A
Loop 3
Loop 2
Loop 1

Does this effect the cBot in any way? My result for fitness comes way before the things the indicator is printing, and the bots are returning 0 fitness when in optimisation. Is is possible to override this effect? (is this the JIT compiler/Loop unrolling)