Issue is fixed in the upcoming WatiN 2.0 beta 1 release

Thanks for reporting.