While that may be a very minor bug in our framework, why are you trying to do this? What purpose does it server in your test automation? LaunchNewBrowser doesn't return until the browser is up and running and our framework has successfully connected to it. I see no value in the code you have written.
Also as a side note, ActiveBrowser.WaitUntilReady only needs to be used after doing some real action in the browser, such as a Navigate or a click that causes the page to change. That API monitors the browsers Ready flag meaning it's done downloading the HTML content and supporting ancillary files. It servers no purpose calling it immediately after LaunchNewBrowser.