I am adding to these answers because my keyword search, 'Why does SQLSvr still believe my dropped tabled exists?', brought me here for what I thought was the same reason. Someone else may also arrive here if same scenario exists.
Using Kennith Fisher's snippet my 'table_name' was not in sys.objects.
SELECT object_schema_name(object_id), name
FROM sys.objects
WHERE name = 'TitleMasters'
I looked closely at my create table's error messages. Turns out I had accidentally created a primary key in a different table with the same name. Kennith's snippet verified this.
SELECT object_schema_name(object_id), name
FROM sys.objects
WHERE name = 'PK_TitleMasters'
I renamed the Primary Key in other table correctly. Then of course my Create Table worked.
So, in the scenario table does not exists in sys.objects be sure its not complaining about a key, constraint, etc. So check whatever object comes up as 'already exists', then delete/rename, whatever is appropriate. This will unblock your new table creation.
Adam S.