The *same* task cannot take part in multiple iterations. *Similar* tasks
might occur, but a task is a block of work taking place between time A and
time B. It requires both the type of work and the start and end time frame
to define a task. A repetition, with the same sort of work taking place
between time C and time D, a different time frame, is actually a different
task even though it may have the same name. After all, if I have to repeat
the widget waxing I could put substitute a new resource for the second
round. Since the purpose of the plan is to produce a schedule, every
iteration of the tasks must appear individually at the time frame where they
will be scheduled to occur. Otherwise, you have no way to advise the
resources when they will be expected to engage in that particular activity.
This means you really can't put in an iteration as a task with a counter
because that will appear in the schedule at only one spot rather than
recurring for each iteration. The best way might be to make a best-guess,
worst-case scenario of the number of interations likely and enter them all
in the plan. Then when you get closer to the events you can refine your
estimate and add or remove iterations as needed.