I think there is value in understanding how your code is going to
run, or is going to run most times, and picking constructs which are
clearly efficient if it's really not more work to do so and it
represents the data you're working with.
Of course, no discussion of NSArray capacities would be complete
without a mention of this post on ridiculousfish:
