The only cases I know of where it's better to turn it off are very large tables that are frequently changed and need to sustain maximum performance. In those instances the performance hit of an auto stats update is enough to be detrimental.
I'd leave it on. You can trace auto stats events and log them for future reference, if you see performance issues that occur during those times you can look at disabling it.