Probably not. Nor should you even want to do this.
For starters, any time you have to declare a variable in your view you're probably doing something wrong. Views should really just bind to their backing models, at most with some conditional or looping logic.
Take a step back and ask... What would this really achieve? You'd save a few keystrokes, but you'd make the code less standard and more difficult to follow. Keystrokes aren't the difficult part. Typing code into an IDE isn't the difficult part. Supporting that code later (either being supported by somebody else or even by yourself some time after you wrote it and forgot about it) is the difficult part.
Keep the code simple, easy to read, easy to understand, and clear and expressive about what it's doing. This code tells you exactly what it's doing:
@Html.TextBoxFor(x => x.Secondbit.C)
It's creating a text box for the C property of the Secondbit property of the model.
Now, if the model is starting to have too many properties and the view is starting to become too large, one thing you can (and depending on the situation perhaps should) do is break apart your view into multiple partial views, each of which addresses a particular model in your large composite model.
For example, you might create a partial view which specifically builds markup for viewing and/or editing a model of type Firstbit. Then in your parent view you'd delegate that model instance to the partial view:
@Html.Partial("FirstbitView", Model.Firstbit)
After all, since the model is a composite of smaller models, it makes sense for the view to be a composite of smaller views. This organizes the code into discrete components rather than into some kind of shorthand notation on a single component.