Issue Description:

As noted here, for an operation like concurrentMap to be efficient, it is forced to explicitly choose a batch size instead of letting Dispatch divide the work up intelligently. That could be solved if there was a concurrentPerform whose closure took a batch start offset and length.

Dispatch could even adaptively adjust batch sizes as it observes the performance of the closure—assuming we can figure out how to do that 😉