There should be a printing somewhere - for mainboards it should be between the expansion slots or near the RAM slots.
There are multiple strategies to measure CPU time: you may use special tools called profilers to employ CPU sampling or develop a microbenchmark to test the suspicious piece of the code. Then, print-statement, called on a money-market-account, will print a basic account statement, output by the primary method specialized on bank-account, followed by details output by the :after methods specialized on savings-account and checking-account.
The disadvantage is that you don't get fine-grained control over the order in which the auxiliary methods run--if you wanted the checking-account part of the statement to print before the savings-account part, you'd have to change the order in which the money-market-account subclasses those classes.
In that case, the rule that subclasses are more specific than their superclasses isn't enough to order all the superclasses. This rule is admittedly somewhat arbitrary but does allow every class to have a linear class precedence list, which can be used to determine which superclasses should be considered more specific than others.
Common Lisp also supports multiple inheritance--a class can have multiple direct superclasses, inheriting applicable methods and slot specifiers from all of them.