Has anyone created multiple tasks in 1 state of a state machine workflow (with
events to listen for each of their completion) before moving to another state?
This would be so the users can complete them in parallel before the workflow
moves on.

Details:
I am trying to create a state machine approval workflow, where many people
approve via tasks. At one point, multiple people (determined at runtime, so
unknown #) need to be assigned a task in parallel so when they are all finished,
the workflow moves on. I have read that there are many issues with doing
replicators or parallel tasks in a state machine (1 state can't have multiple
event handlers for the tasks, etc,
www.pseale.com/.../...orkflowNuttinessVolume1.aspx), and that I
should switch it to sequential, however state fits the requirements of
everything else better.

I saw a few things online of ways to do it, but they are not working for me
(social.msdn.microsoft.com/.../56389fd\
8-4cef-41d3-9db8-e5b42cbc76ff).