Are there drawbacks to creating a class that encapsulates Generic Collection?

A part of my (C# 3.0 .NET 3.5) application requires several lists of strings to be maintained. I declare them, unsurprisingly, as List and everything works, which is nice.

The strings in these Lists are actually (and always) Fund IDs. I'm wondering if it might be more intention-revealing to be more explicit, e.g.:

public class FundIdList : List<string> { }

... and this works as well. Are there any obvious drawbacks to this, either technically or philosophically?