Bug fix: convert captured multiplier to a number

This explains the discrepancy noted earlier: instead of adding numbers,
the computation concatenated strings.

As a result, the total number of computations was compared as a string
value, using lexical rather than numerical order.