separate assembly

[Stephen Weeks]

> Bottom line is that it is useful to have the timing information of a pass
> over all the chunks in order to note which phases could be improved, but
> I don't know if I can calculate that.  Looking through Control and Trace I
> couldn't find a version that would calculate the total computation for all
> calls to a function and then print the time at the end.

There isn't one.  I'll have to think for a bit about the right interface.  For
now, I'd just roll my own stuff to sum up the times.  You should still use
Control.traceCall to print the results.