The problem is well-known since SQL Server 2005 ( 2000 maybe ).
For some explanations, please, could you have a look at this link ?
With my knowledges about the SQL Server Management Team, this problem will always be there in the versions appearing after 2015.
The solution is given in this link to drop and recreate the stored procedure : a solution simple for Microsoft but stupid for a DBA
It seems you will find the explanation with this link :
Even if the thread is related to the rename of a table and not reported in the stored procedure using this table, i think the explanation could be the same.
commented on Aug 17 2011 3:27PM