storage? any one of many compression techniques. Think '.zip' or RLE or bit vectors or ....

efficiency? Your usual choices are usually valid, but would you consider them the best measure of the "efficiency" of producing a one-off or rarely used program? Being concerned solely with "cpu and time^Update1 consumption" and ignoring "programmer time" might be a serious case of premature optimization.

Update 1: I assume from context that the "time" reference meant "run time."