Is it appropriate to create a Service explicitly via constructor?
<p>I know that all application components shouldn't be instantiated directly and I should use <code>startService</code> or <code>bindService</code> for interacting with <code>Service</code>. But in Google sample showing how to implement in-app billing version 2 I can see that <code>Service</code> is created directly in Dungeons.java at line 259:</p>

<pre><code>mBillingService = new BillingService();
mBillingService.setContext(this);
</code></pre>

<p><code>BillingService</code> class extends <code>android.app.Service</code> and is registered in manifest as service.</p>

<p>But <code>BillingService</code> object is just created instead of binding. So I wonder was it a bug in official sample or is it really suitable way for local services?</p>
