Wow...that is the first time I have heard that. The number one thing is ease of date entry. When we tried to use the standard .NET wrapped DateTimepicker in our medical application, we had hate mail coming our way...a lot of it! In fact, we had several other internal applications that used that control...and we got hate mail from them too. In fact, I sent my self some hate mail when I had to use it in the real-world. Once we released the DateBox control in our medical application our users sent us some love notes The ease of date entry was the main purpose behind it. Not to mention total control. We can enhance this control and do whatever we want with it. It truth, the standard DateTimepicker is okay if you are just going to have some simple dates popped up there that are not a major piece of your app. But when it comes to heads down entry and large date entry, it makes a huge difference.
Not that it matters at this point, but we also got some not quite hate mail but definitely not love notes from a number of SF users as well that were passing along complaints from their users.
I will create a demo at some point, but there is a lot of intelligence in the DateBox that isn't in the DateTimePicker. For example, in the DateBox, I can enter the control and type "5560" and it will input "05/05/1960" into the control. It has the inteligence to figure this type of thing out. You could also type "010180" and it would put "01/01/1980." Let me put it like this, I was grilled by QA until we made the QA team smile...and it ain't easy to do that!
As for the clear command, I will most likely expose this property in the next update and you can do as you like. This makes sense anyway.