Posted 08 May 2013 - 01:13 AM
One thing you'll learn about programming - especially .NET: there are many different ways to do things, and there often isn't any one "correct" way.
It's been a while since I've looked at that particular exercise, but just off the top of my head, both ideas sound completely feasible to me. I couldn't tell you why the writer of the book went with one implementation over the other, in part they're also trying to cater to the expected skill level at that point in the book, but I can tell you that I could think of about a thousand other ways to implement it too.
In a more complex application, there would be more variables to consider when deciding on an implementation (how other components will work together, performance, thread safety, etc) that could limit your choices more, but with "day at the races" there are a lot of options.