Ashley,
r246 was definitely affected. Probably r244 too, but I don't remember for sure.
I first noticed this about 30 days ago, when I started using C2 on this laptop with Windows 10.
I included information about that experiment with bat file as I hope it might be useful. It's obviously a synthetic test and not a real usage case. But it demonstrates that it's not the windows uptime (or not just the uptime) which is causing these lags, but also the number of times C2 was launched.
Also, you could probably try to leave a similar script running on a Windows 10 PC with all recent updates overnight, and check next morning if C2 is running slow or not.
I understand, that an app should be starting from a blank slate, and I've never seeing anything like this with other applications. So maybe C2 leaves something behind after closing that's slowing it down over time? (temporary files, some processes in memory, open files or something like that?)
For example, after that experiment I found that C2 created lots of temporary folders, 400Mb in total, many of which contained copies of project files in \Documents and Settings\{profile}\Local Settings\Temp
Unfortunately, removing these folders didn't improve the performance. Only rebooting Windows seems to help.