If, for some reason like exceptions or other conditions, the execution count is not met within the flow, the counter is not reset. Thus, next time the flow is executed it will start with the count from the last execution.
To use Execution Count for reliable loops it should be possible to optionally reset the internal counter at each flow start.
The count parameter should accept variables like "{length(someList)}".
The current value of the internal counter should be optionally stored in a variable (the name of which would be supplied by the user).
Together this would greatly simplify the construction of loops in our flows.