C# 5 async/await thread mechanics feel wrong?

Question

Why have the calling thread walk into the async method until the inner \'await\'?

Isn\'t it cleaner to just spawn a thread as soon as an async method is called. That way

Answer 1

I tend to like to know whether a method is going to execute code on 'my' thread or not.

I think that is a peculiar desire, not really a good argument for/against any feature.

The main point of async/await is that the code for starting an async op and handling the results can be kept into one method.

Without it you are forced to break code that logically belongs together into 2 parts.