(which I presume is the time spent generating the plan).
That's the time spend by SSMS rendering the plan, before it runs out of memory (or hits max resultsets) and gives up.
There's no good reason to display a plan of a procedure like that, you can't really demonstrate much from a plan of a cursor, just lots and lots and lots of repetition of the same piece of the plan.
Maybe use performance characteristics to teach this lesson and show him exec plans of something simpler?
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)SQL In The Wild
: Discussions on DB performance with occasional diversions into recoverability
We walk in the dark places no others will enter
We stand on the bridge and no one may pass