This is a crude way to work around a change in the Amazon API. Specifically, SQS no longer allows a user to create, delete and then create again a queue of the same name within 60 seconds. Is there a more sophisticated way to ensure that test cases execute a minimum of 60-61 seconds apart? 
This is in essence a problem with the approach of designing the functional test cases to setup, execute and tear down for each API call: for some (particularly cloud) APIs, this is viewed as an invalid series of calls, because there is no plausible scenario when someone would want to perform such a series of activities functionally, and increasingly the APIs are building in the ability to deny such a call as invalid.