The table will fall under your ownership. The table may not be visible or useable by other logins. If there is another table by the same name belonging to the dbo, then code executed by you will use your table while code executed by the dbo or other logins will use the dbo-owned table.
Its best to avoid this unless for some reason you need to store private data in the database.
If it's not practically useful, then it's practically useless.
I know there may be a need to have different owners for different objects...
1). I have just never found one
2). I've seen 3rd party vendors do this, when a simple different table name would have been better
3). It makes maintanence a nightmare
4). It does force me to write bullet proof utilities